## Pre-Installation Checklist

Before plugging in the 9600 Series IP Telephone, verify that all the following requirements are met. Failure to do so prevents the telephone from working properly and can have a negative impact on the network. Print copies of this checklist for each server and IP telephone.

Verify These Network Requirements
| 1. | Ensure that the LAN uses Ethernet Category 5e cabling running the IPv4 version of Internet Protocol.
| 2. | Avaya Communication Manager Release 3.0 or later software supports the 9600 Series IP Telephones, aliased as 4600 Series IP Telephones. Specifically, the 9620 should be aliased as a 4610 and the 9630 should be aliased as a 4620.
| 3. | The following circuit packs are installed on the switch: TN2602 IP Media Processor circuit pack. Sites with a TN2302 IP Media Processor circuit pack must also install a TN2602 circuit pack. TN799B, C, or D Control-LAN (CLAN) circuit pack
| 4. | The Avaya Media Server is configured correctly, as described in the Avaya one-X Deskphone Edition for 9600 Series IP Telephones Administrator Guide and Avaya Communication Manager documentation. Both documents are available at http://www.avaya.com/support.
| 5. | The DHCP server and application are administered as described in the Avaya one-X Deskphone Edition for 9600 Series IP Telephones Administrator Guide.
| 6. | The HTTP server and application are administered as described in the Avaya one-X Deskphone Edition for 9600 Series IP Telephones Administrator Guide.
| 7. | The upgrade script and application files from the Avaya Support Web site, http://www.avaya.com/support, are loaded correctly on the HTTP/HTTPS server.
| 8. | If applicable, the DNS server is administered as described in the Avaya one-X Deskphone Edition for 9600 Series IP Telephones Administrator Guide.
| 9. | If applicable, the WML server is administered as described in the Avaya one-X Deskphone Edition for 9600 Series IP Telephones Administrator Guide.
| Notes: |
Any or all of the server applications mentioned in items 5.-9. can be co-resident on the same hardware, subject to the specific restrictions of each individual application. See the Avaya one-X Deskphone Edition for 9600 Series IP Telephones Administrator Guide for more information about:
NOTE: | administering other network equipment, administering applications like firewalls, and information about topics like port utilization.

Requirements to Verify for Each IP Telephone
| 10. | You have an extension number and an Avaya Communication Manager security code (password) for each applicable IP telephone. If your call server supports unnamed registration, and the telephone settings file allows unnamed registration, you do not need to provide an extension or password for the telephone. However, if you do not provide an extension or password, the telephone will have very limited telephone functionality. (For information, see Unnamed Registration.)
| 11. | A Category 5e LAN jack is available at each telephone site.
| 12. | Electrical power is provided to each telephone by a Telephone Power Module (DC power jack) (must be ordered separately). If the LAN will supply IEEE-standard power to the telephone, no power module is required.

| 13. | 1 Category 5e modular line cord is available for the connection between the IP telephone and the PC, if applicable.
| 14. | Verify that the 9600 Series IP Telephone package includes the following components: 1 telephone set with pre-attached stand. 1 handset capable of transmitting and receiving 7KHz audio. 1 H4DU 9-foot long (when extended) 4-conductor coiled handset cord, plugged into the telephone and the handset. 1 Category 5 modular line cord for the connection from the IP telephone to the Ethernet wall jack. Avaya one-X Deskphone Edition for 9600 Series IP Telephones Safety Instructions. Avaya one-X Deskphone Edition for 9600 Series IP Telephones Stand Instructions. Avaya one-X Deskphone Edition for 9600 Series IP Telephones Wall Mount Instructions.

NOTE: For sites using headsets, the 9600 Series IP Telephones support only the HIS headset cords.